@jtnord thanks very much for running this build. It shows a problem that is unrelated to this change but will affect this week's plugin BOM build.

The ci.jenkins.io agents that run these builds have now upgraded to command line git 2.51.0. That's a desirable change, but it shows a bug in git client plugin releases prior to 6.3.1. Prior to 6.3.1, the git client plugin assumes the "git whatchanged" command is available. Command line git 2.51.0 drops the "git whatchanged" command.

Git client plugin 6.3.0 and later require Jenkins 2.504.1. That means tests of the 2.492.x line are using a git client plugin version that does not support CLI git 2.51.0.

Alternatives that come to mind:

• Drop support for the 2.492.x line from the plugin BOM. We're 6 weeks away from dropping that line in the usual cadence, so it is not too early to drop the line (this seems like the easiest option and is my preference)
• Ask the infra team to switch the Jenkins agents back to CLI git 2.50.x instead of 2.51.0. They would need to reject the 2.51.0 upgrade until the 2.492.x line is dropped from the plugin BOM
• Release a new version of the git client plugin that support Jenkins 2.492.x. That is more complicated than might be expected because the transition to 2.504.x was so that the git client plugin could rely on the plugin BOM for Apache Mina SSHD 2.16.0 and Apache Mina SSHD 2.16.0 is only available in plugin BOM 2.504.x and newer

There may be other options as well.

@basil or @darinpope do you have any alternative recommendations?

My preference is for a backport of jenkinsci/git-client-plugin#1327 to the 2.492.x line, since this affects production users as well.

⇒ jenkinsci/git-client-plugin#1332

Beware of github-api that might require a release to support jackson 2.20.0. See

• fix: remove usage of a deprecated constant. hub4j/github-api#2138
• Runtime errors when using jackson 2.20.0 hub4j/github-api#2137

@jtnord These plugins have been released and adopted in BOM:

• https://github.com/jenkinsci/github-api-plugin/releases/tag/1.330-492.v3941a_032db_2a_
• https://github.com/jenkinsci/gitlab-plugin/releases/tag/gitlab-plugin-1.9.9

The most recent PR build is passing except for a failure in org.jenkinsci.plugins.gitclient.GitClientTest#testSparseCheckoutWithCliGitLFS. That seems to be an infrastructure-related flake, as I cannot reproduce the failure locally.

As far as references to com.fasterxml.jackson.databind.PropertyNamingStrategy in jenkinsci are concerned, I see at least one in kubernetes-pipeline-plugin (known to be dead/non-functional) and one in tests for gerrit-code-review-plugin (so not a production issue, and not an issue for BOM or CloudBees CI). The latter only has 1,000 installations, so I don't feel strongly about proactively migrating it. Other usages exist but only in very low install counts.

From an open-source Jenkins perspective, I think jenkinsci/jackson2-api-plugin#311 is ready for merge/release.

From an open-source Jenkins perspective, I think jenkinsci/jackson2-api-plugin#311 is ready for merge/release.

Many thanks for the analysis and the reminder

Closing this pull request because gitlab-api has been updated to handle Jackson 2.20.0. The updated version will be included in the next release of the plugin BOM.

Refer to JENKINS-76091 and its linked pull requests for more details.